-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
protocols: implement image-capture-source-v1 and image-copy-capture-v1 #11709
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
c07137b to
0169424
Compare
|
I almost shat myself and thought someone random would write a bad impl then I noticed it's ikalco 🥰 I think we should unify screencopy at this point. Protocol files should have 0 rendering code, and instead that would be delegated to a global sharing mgr. One MR is ok. Maybe keep commits making sense though.
black until allowed/denied, if denied keep rendering black but with a "screencast denied" text. IIRC thats how it is rn. |
|
ping me for review when ready |
94f3b2f to
861fd28
Compare
7ea28e1 to
bba00a6
Compare
|
I could help out with this if wanted. I already hacked together a complete implementation for Hyprland 2 months ago or so to test out a library I'm working on. Every compositor either had a poor implementation or an incomplete one so I couldn't test anything reliably. |
77ba086 to
09ce282
Compare
1bf6cc0 to
9f6abae
Compare
9f6abae to
558f178
Compare
558f178 to
4615e8a
Compare
4615e8a to
19f32ae
Compare
Describe your PR, what does it fix/add?
implement the image-capture-source-v1 and image-copy-capture-v1 protocols
Is there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)
do you want me to split into separate PRs?
also how should we do permissions?
either error on image source creation, or do like screencopy and allow the source but render denied screen
Is it ready for merging, or does it need work?
ready from my testing